fmt: Ran cargo +nightly fmt --all after new nightly release. - #10081
fmt: Ran cargo +nightly fmt --all after new nightly release.#10081genericusername2709 wants to merge 2 commits into
cargo +nightly fmt --all after new nightly release.#10081Conversation
5369d30 to
86499dc
Compare
cargo +nightly fmt --all after new nighly build release.cargo +nightly fmt --all after new nightly release.
86499dc to
40fae22
Compare
40fae22 to
1a37ead
Compare
josephlou5
left a comment
There was a problem hiding this comment.
I do like it when formatters automatically wrap comments (yay clang-format) but this is such a (necessarily) big commit lol.
I've reviewed 42 files but will take a break here in case a maintainer wants to tell me to knock it off with the reflow requests and just submit the commit as-is.
60c02ce to
fd34fcc
Compare
cf7f67c to
62be36e
Compare
48056ac to
431822a
Compare
|
Do you know if this |
I know this is still a nightly feature but it's kind of ridiculous how inconsistently it behaves. I've reviewed 150 files and still can't figure out why sometimes it breaks lines weirdly and doesn't fill out to 80 columns. Maybe disabling the option would be better... |
431822a to
cc67038
Compare
|
It is a reported bug in |
cc67038 to
a877d5d
Compare
That doesn't seem related; that issue is talking about multi-line block comments using |
0251a6b to
6619cf4
Compare
6619cf4 to
4bc9ed9
Compare
4bc9ed9 to
87b7340
Compare
|
Looks like the comment width is now calculated including indents, but I haven't double-checked. |
Github action
check(rustfmt)failing after new nightly releaseRan the command
cargo +nightly fmt --allto fix the format.Checklist
If applicable:
how it works, how it's organized), including any code drafted by an LLM.